S3Drive - Corrupted on Transfer - IDrive MD5 Hashes Differ

Hey i keep getting MD5 hashs differ errors when using a sync job with the windows client. Ive reached out to IDrive to see if this is something that is just a matter of me adjusting my bucket or if this is a source issue. Hoping to get some direction on things to try to identify what the cause of this is. During my testing i can create a .txt file and right away it gives a hash mismatch. When i try and force a sync again it causes the source hash to change every time. Its happening from multiple endpoints as well.

Hi! Thanks for your feedback. We remember similar issue present in the past for iDrive when their server-side encryption is enabled. Can you let me know if you use their SSE? Do you use S3Drive built-in E2E encryption? Please specify your iDrive endpoint, in principal S3Drive tries to detect iDrive and then applies specific settings to overcome some problems, perhaps this hasn't worked as it should in this case. Thanks!

Sorry to weigh in, I often get this aswell, I have default encryption on and here is a demo endpoint engine.i7b0.ldn.idrivee2-69.com

That would totally make sense if that's the case, let me toggle it off on their side or make a new bucket and then I'll try and do some backing up and see if that causes the issue to go away. I'm using idrives for my main bucket and in another instance im using your encryption with idrives also turned on. Both instances seem to have the issue

3:05 PM

It looks like that fixed the issue, maybe you could put in a check under settings for providers and then set a flag for disabling the md5 has verification? Because turning off md5 verification doesn't stop this error

In a next release there will be configurable setting in the: Profile settings Currently this prompt is only available when you configure mount on desktop. It will be available for iDrive or AWS endpoints on all platforms (mobile and desktop).

thats awesome!! love your product so far, cant wait to see whats to come.

Hi @cromeanator, I've wanted to confirm with you if this is now solved?

I solved it by just disabling the idrive side encryption but I saw you added a setting to detect SSE so I'll have to do some testing and see if the same issue occurs. Ether way I'm all set!